Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check if we need to link against libatomic #84

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

bbockelm
Copy link
Collaborator

On some 32-bit platforms, explicit linking against libatomic is required for atomics to be utilized. Test that at the CMake level, adding an import target as we did for std::filesystem that can be used.

Based on the suggestion from:
#81

On some 32-bit platforms, explicit linking against libatomic is
required for atomics to be utilized.  Test that at the CMake level,
adding an import target as we did for `std::filesystem` that can
be used.

Based on the suggestion from:
PelicanPlatform#81
@bbockelm
Copy link
Collaborator Author

@ellert - apologies for the delay. Can you please test this PR as an alternative solution to #81?

Basically, your CMake contribution was migrated to a separate file and then we link against the target, avoiding CMake variables.

@ellert
Copy link
Contributor

ellert commented Jan 31, 2025

Can you please test this PR

It works.

@bbockelm bbockelm merged commit d75b46d into PelicanPlatform:main Jan 31, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants